Storage tier verification checks

ABSTRACT

Techniques are provided for storage tier verification checks. A determination is made that a mount operation of an aggregate of a set of volumes stored within a multi-tier storage environment has completed. A first metafile and a second metafile are maintained to track information related to the storage of objects of a volume of the aggregate within a remote object store that is a tier of the multi-tier storage environment. A distributed verification is performed between the first metafile and the second metafile to identify an inconsistency. Accordingly, the first metafile and the second metafile are reconciled to address the inconsistency so that storage information within the first metafile and the second metafile are consistent.

RELATED APPLICATIONS

This application claims priority to and is a continuation of U.S.application Ser. No. 15/624,891, filed on Jun. 16, 2017, now allowed,titled “STORAGE TIER VERIFICATION CHECKS,” which is incorporated hereinby reference.

BACKGROUND

Many storage systems may provide clients with access to data storedwithin a plurality of storage devices. For example, a storage controllermay store client data within a set of storage devices that are locallyaccessible (e.g., locally attached to the storage controller) orremotely accessible (e.g., accessible over a network). A storageaggregate of storage (e.g., a composite aggregate comprising a set ofvolumes) may be generated from the set of storage devices (e.g., thestorage aggregate may be stored across one or more storage devices). Thestorage aggregate may be exported from a storage file system to aclient. The storage aggregate may appear as one or more storagecontainers to the client, such as a volume or logical unit number (lun).In this way, the storage aggregate abstracts away the details, from theclient, of how the storage aggregate is physically stored amongst theset of storage devices.

Some storage systems may store data within a multi-tiered storageenvironment. For example, the storage controller may store data within ahard disk drive tier and a solid state storage tier. The hard disk drivetier may be used as a capacity tier to store client data and forprocessing input/output operations. The solid state storage tier may beused as a cache for accelerating the processing of storage operations.Different storage tiers have different characteristics and behaviors,which can affect performance and guarantees provided to clients by astorage system.

In an example, a storage system may utilize a storage tier (e.g., alocal storage tier hosted, owned, and/or managed by one or more nodes ofa storage environment associated with the storage system) and a remoteobject store as two of the storage tiers within which the storage systemstores data. The storage system may be able to provide highavailability, security, data consistency, data protection, and/or otherguarantees using the storage tier because the storage system may manageand control the storage tier. However, the storage system may be unableto provide similar guarantees, such as that data is properly stored,managed, is consistent, and is accurate, to clients for the remoteobject store because the storage system does not manage and control theremote object store (e.g., a third party provider may host and managethe remote object store). For example, new data could be written to aremote third party object store. When reading the new data, old data orno data could be returned by the remote third party object store due todelay. Thus, the storage system may be unable to provide the same levelof enterprise guarantees and efficiencies when working with the remotethird party object store as backend storage.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a component block diagram illustrating an example clusterednetwork in accordance with one or more of the provisions set forthherein.

FIG. 2 is a component block diagram illustrating an example data storagesystem in accordance with one or more of the provisions set forthherein.

FIG. 3 is a flow chart illustrating an exemplary method of storage tierverification checks.

FIG. 4 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks.

FIG. 5 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where a volume informationmetafile and a storage area information metafile are verified.

FIG. 6 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where a buftree layout isverified.

FIG. 7 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where a staging areainformation metafile and a staging area metafile are verified.

FIG. 8 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where a staging areainformation metafile and an object information metafile are verified.

FIG. 9 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where a volume informationmetafile and an object information metafile are verified.

FIG. 10 is a component block diagram illustrating an exemplary computingdevice for storage tier verification checks, where an object referencemetafile and an object map metafile are verified.

FIG. 11 is an example of a computer readable medium in accordance withone or more of the provisions set forth herein.

DETAILED DESCRIPTION

Some examples of the claimed subject matter are now described withreference to the drawings, where like reference numerals are generallyused to refer to like elements throughout. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide an understanding of the claimed subject matter. It maybe evident, however, that the claimed subject matter may be practicedwithout these specific details. Nothing in this detailed description isadmitted as prior art.

One or more techniques and/or computing devices for storage tierverification checks are provided herein. A storage system may utilizemultiple tiers of storage to store client data. For example, the storagesystem may utilize a first storage tier (e.g., a performance storagetier, such as a solid state storage tier or a hard disk drive storagetier, locally hosted and/or maintained by nodes of a storage environmentassociated with the storage system), a second storage tier such as aremote object store (e.g., a distributed network of storage provided bya third party provider, a capacity tier, cloud storage, etc.), and/orother tiers of storage.

Unfortunately, the remote object store may not provide adequateguarantees of data validity and consistency that the storage systemguarantees for clients. For example, the remote object store may returnold data instead of newly written data due to delays. In anotherexample, the remote object store may return an object not found responsefor the newly written data due to delays. Other issues can arise whenmetafiles used by the storage system to manage the storage of object tothe remote object store become corrupt or inconsistent.

Accordingly, as provided herein, storage tier verification checks ofmetafiles and/or other information is provided by the storage system. Inparticular, a volume information metafile and/or a staging areainformation metafile are verified during a mount operation of a volume.A distributed verification of other metafiles, such as an objectinformation metafile, a staging area metafile, an object referencemetafile, and/or an object map metafile, may be delayed until after themount operation. Client access operations may be allowed during thedistributed verifications.

Because the volume information metafile and/or the staging areainformation metafile may be relatively quick and efficient to verify,such verification can be performed during the mount operation withoutintroducing significant delay for completing the mount operation.Reducing the time to complete the mount operation is beneficial becauseclients cannot access the aggregate until after the mount operation hascompleted. Any inconsistencies identified during the verifications maybe addressed (e.g., information within a metafile may be cleared ormodified to make the metafile consistent with other metafiles) so thatthe metafiles are consistent.

To provide for storage tier verification checks, FIG. 1 illustrates anembodiment of a clustered network environment 100 or a network storageenvironment. It may be appreciated, however, that the techniques, etc.described herein may be implemented within the clustered networkenvironment 100, a non-cluster network environment, and/or a variety ofother computing environments, such as a desktop computing environment.That is, the instant disclosure, including the scope of the appendedclaims, is not meant to be limited to the examples provided herein. Itwill be appreciated that where the same or similar components, elements,features, items, modules, etc. are illustrated in later figures but werepreviously discussed with regard to prior figures, that a similar (e.g.,redundant) discussion of the same may be omitted when describing thesubsequent figures (e.g., for purposes of simplicity and ease ofunderstanding).

FIG. 1 is a block diagram illustrating the clustered network environment100 that may implement at least some embodiments of the techniquesand/or systems described herein. The clustered network environment 100comprises data storage systems 102 and 104 that are coupled over acluster fabric 106, such as a computing network embodied as a privateInfiniband, Fibre Channel (FC), or Ethernet network facilitatingcommunication between the data storage systems 102 and 104 (and one ormore modules, component, etc. therein, such as, nodes 116 and 118, forexample). It will be appreciated that while two data storage systems 102and 104 and two nodes 116 and 118 are illustrated in FIG. 1, that anysuitable number of such components is contemplated. In an example, nodes116, 118 comprise storage controllers (e.g., node 116 may comprise aprimary or local storage controller and node 118 may comprise asecondary or remote storage controller) that provide client devices,such as host devices 108, 110, with access to data stored within datastorage devices 128, 130. Similarly, unless specifically providedotherwise herein, the same is true for other modules, elements,features, items, etc. referenced herein and/or illustrated in theaccompanying drawings. That is, a particular number of components,modules, elements, features, items, etc. disclosed herein is not meantto be interpreted in a limiting manner.

It will be further appreciated that clustered networks are not limitedto any particular geographic areas and can be clustered locally and/orremotely. Thus, in one embodiment a clustered network can be distributedover a plurality of storage systems and/or nodes located in a pluralityof geographic locations; while in another embodiment a clustered networkcan include data storage systems (e.g., 102, 104) residing in a samegeographic location (e.g., in a single onsite rack of data storagedevices).

In the illustrated example, one or more host devices 108, 110 which maycomprise, for example, client devices, personal computers (PCs),computing devices used for storage (e.g., storage servers), and othercomputers or peripheral devices (e.g., printers), are coupled to therespective data storage systems 102, 104 by storage network connections112, 114. Network connection may comprise a local area network (LAN) orwide area network (WAN), for example, that utilizes Network AttachedStorage (NAS) protocols, such as a Common Internet File System (CIFS)protocol or a Network File System (NFS) protocol to exchange datapackets, a Storage Area Network (SAN) protocol, such as Small ComputerSystem Interface (SCSI) or Fiber Channel Protocol (FCP), an objectprotocol, such as S3, etc. Illustratively, the host devices 108, 110 maybe general-purpose computers running applications, and may interact withthe data storage systems 102, 104 using a client/server model forexchange of information. That is, the host device may request data fromthe data storage system (e.g., data on a storage device managed by anetwork storage control configured to process I/O commands issued by thehost device for the storage device), and the data storage system mayreturn results of the request to the host device via one or more storagenetwork connections 112, 114.

The nodes 116, 118 on clustered data storage systems 102, 104 cancomprise network or host nodes that are interconnected as a cluster toprovide data storage and management services, such as to an enterprisehaving remote locations, cloud storage (e.g., a storage endpoint may bestored within a data cloud), etc., for example. Such a node in theclustered network environment 100 can be a device attached to thenetwork as a connection point, redistribution point or communicationendpoint, for example. A node may be capable of sending, receiving,and/or forwarding information over a network communications channel, andcould comprise any device that meets any or all of these criteria. Oneexample of a node may be a data storage and management server attachedto a network, where the server can comprise a general purpose computeror a computing device particularly configured to operate as a server ina data storage and management system.

In an example, a first cluster of nodes such as the nodes 116, 118(e.g., a first set of storage controllers configured to provide accessto a first storage aggregate comprising a first logical grouping of oneor more storage devices) may be located on a first storage site. Asecond cluster of nodes, not illustrated, may be located at a secondstorage site (e.g., a second set of storage controllers configured toprovide access to a second storage aggregate comprising a second logicalgrouping of one or more storage devices). The first cluster of nodes andthe second cluster of nodes may be configured according to a disasterrecovery configuration where a surviving cluster of nodes providesswitchover access to storage devices of a disaster cluster of nodes inthe event a disaster occurs at a disaster storage site comprising thedisaster cluster of nodes (e.g., the first cluster of nodes providesclient devices with switchover data access to storage devices of thesecond storage aggregate in the event a disaster occurs at the secondstorage site).

As illustrated in the clustered network environment 100, nodes 116, 118can comprise various functional components that coordinate to providedistributed storage architecture for the cluster. For example, the nodescan comprise network modules 120, 122 and disk modules 124, 126. Networkmodules 120, 122 can be configured to allow the nodes 116, 118 (e.g.,network storage controllers) to connect with host devices 108, 110 overthe storage network connections 112, 114, for example, allowing the hostdevices 108, 110 to access data stored in the distributed storagesystem. Further, the network modules 120, 122 can provide connectionswith one or more other components through the cluster fabric 106. Forexample, in FIG. 1, the network module 120 of node 116 can access asecond data storage device by sending a request through the disk module126 of node 118.

Disk modules 124, 126 can be configured to connect one or more datastorage devices 128, 130, such as disks or arrays of disks, flashmemory, or some other form of data storage, to the nodes 116, 118. Thenodes 116, 118 can be interconnected by the cluster fabric 106, forexample, allowing respective nodes in the cluster to access data on datastorage devices 128, 130 connected to different nodes in the cluster.Often, disk modules 124, 126 communicate with the data storage devices128, 130 according to the SAN protocol, such as SCSI or FCP, forexample. Thus, as seen from an operating system on nodes 116, 118, thedata storage devices 128, 130 can appear as locally attached to theoperating system. In this manner, different nodes 116, 118, etc. mayaccess data blocks through the operating system, rather than expresslyrequesting abstract files.

It should be appreciated that, while the clustered network environment100 illustrates an equal number of network and disk modules, otherembodiments may comprise a differing number of these modules. Forexample, there may be a plurality of network and disk modulesinterconnected in a cluster that does not have a one-to-onecorrespondence between the network and disk modules. That is, differentnodes can have a different number of network and disk modules, and thesame node can have a different number of network modules than diskmodules.

Further, a host device 108, 110 can be networked with the nodes 116, 118in the cluster, over the storage networking connections 112, 114. As anexample, respective host devices 108, 110 that are networked to acluster may request services (e.g., exchanging of information in theform of data packets) of nodes 116, 118 in the cluster, and the nodes116, 118 can return results of the requested services to the hostdevices 108, 110. In one embodiment, the host devices 108, 110 canexchange information with the network modules 120, 122 residing in thenodes 116, 118 (e.g., network hosts) in the data storage systems 102,104.

In one embodiment, the data storage devices 128, 130 comprise volumes132, which is an implementation of storage of information onto diskdrives or disk arrays or other storage (e.g., flash) as a file-systemfor data, for example. In an example, a disk array can include alltraditional hard drives, all flash drives, or a combination oftraditional hard drives and flash drives. Volumes can span a portion ofa disk, a collection of disks, or portions of disks, for example, andtypically define an overall logical arrangement of file storage on diskspace in the storage system. In one embodiment a volume can comprisestored data as one or more files that reside in a hierarchical directorystructure within the volume.

Volumes are typically configured in formats that may be associated withparticular storage systems, and respective volume formats typicallycomprise features that provide functionality to the volumes, such asproviding an ability for volumes to form clusters. For example, where afirst storage system may utilize a first format for their volumes, asecond storage system may utilize a second format for their volumes.

In the clustered network environment 100, the host devices 108, 110 canutilize the data storage systems 102, 104 to store and retrieve datafrom the volumes 132. In this embodiment, for example, the host device108 can send data packets to the network module 120 in the node 116within data storage system 102. The node 116 can forward the data to thedata storage device 128 using the disk module 124, where the datastorage device 128 comprises volume 132A. In this way, in this example,the host device can access the volume 132A, to store and/or retrievedata, using the data storage system 102 connected by the storage networkconnection 112. Further, in this embodiment, the host device 110 canexchange data with the network module 122 in the node 118 within thedata storage system 104 (e.g., which may be remote from the data storagesystem 102). The node 118 can forward the data to the data storagedevice 130 using the disk module 126, thereby accessing volume 1328associated with the data storage device 130.

It may be appreciated that storage tier verification checks may beimplemented within the clustered network environment 100. In an example,the node 116 and/or the node 118 may utilize a multi-tier storageenvironment such as a remote object store and/or the data storagedevices 128, 130 for serving client requests. It may be appreciated thatstorage tier verification checks may be implemented for and/or betweenany type of computing environment, and may be transferrable betweenphysical devices (e.g., node 116, node 118, a desktop computer, atablet, a laptop, a wearable device, a mobile device, a storage device,a server, etc.) and/or a cloud computing environment (e.g., remote tothe clustered network environment 100).

FIG. 2 is an illustrative example of a data storage system 200 (e.g.,102, 104 in FIG. 1), providing further detail of an embodiment ofcomponents that may implement one or more of the techniques and/orsystems described herein. The data storage system 200 comprises a node202 (e.g., nodes 116, 118 in FIG. 1), and a data storage device 234(e.g., data storage devices 128, 130 in FIG. 1). The node 202 may be ageneral purpose computer, for example, or some other computing deviceparticularly configured to operate as a storage server. A host device205 (e.g., 108, 110 in FIG. 1) can be connected to the node 202 over anetwork 216, for example, to provide access to files and/or other datastored on the data storage device 234. In an example, the node 202comprises a storage controller that provides client devices, such as thehost device 205, with access to data stored within data storage device234.

The data storage device 234 can comprise mass storage devices, such asdisks 224, 226, 228 of a disk array 218, 220, 222. It will beappreciated that the techniques and systems, described herein, are notlimited by the example embodiment. For example, disks 224, 226, 228 maycomprise any type of mass storage devices, including but not limited tomagnetic disk drives, flash memory, and any other similar media adaptedto store information, including, for example, data (D) and/or parity (P)information.

The node 202 comprises one or more processors 204, a memory 206, anetwork adapter 210, a cluster access adapter 212, and a storage adapter214 interconnected by a system bus 242. The data storage system 200 alsoincludes an operating system 208 installed in the memory 206 of the node202 that can, for example, implement a Redundant Array of Independent(or Inexpensive) Disks (RAID) optimization technique to optimize areconstruction process of data of a failed disk in an array.

The operating system 208 can also manage communications for the datastorage system, and communications between other data storage systemsthat may be in a clustered network, such as attached to a cluster fabric215 (e.g., 106 in FIG. 1). Thus, the node 202, such as a network storagecontroller, can respond to host device requests to manage data on thedata storage device 234 (e.g., or additional clustered devices) inaccordance with these host device requests. The operating system 208 canoften establish one or more file systems on the data storage system 200,where a file system can include software code and data structures thatimplement a persistent hierarchical namespace of files and directories,for example. As an example, when a new data storage device (not shown)is added to a clustered network system, the operating system 208 isinformed where, in an existing directory tree, new files associated withthe new data storage device are to be stored. This is often referred toas “mounting” a file system.

In the example data storage system 200, memory 206 can include storagelocations that are addressable by the processors 204 and adapters 210,212, 214 for storing related software application code and datastructures. The processors 204 and adapters 210, 212, 214 may, forexample, include processing elements and/or logic circuitry configuredto execute the software code and manipulate the data structures. Theoperating system 208, portions of which are typically resident in thememory 206 and executed by the processing elements, functionallyorganizes the storage system by, among other things, invoking storageoperations in support of a file service implemented by the storagesystem. It will be apparent to those skilled in the art that otherprocessing and memory mechanisms, including various computer readablemedia, may be used for storing and/or executing application instructionspertaining to the techniques described herein. For example, theoperating system can also utilize one or more control files (not shown)to aid in the provisioning of virtual machines.

The network adapter 210 includes the mechanical, electrical andsignaling circuitry needed to connect the data storage system 200 to ahost device 205 over a network 216, which may comprise, among otherthings, a point-to-point connection or a shared medium, such as a localarea network. The host device 205 (e.g., 108, 110 of FIG. 1) may be ageneral-purpose computer configured to execute applications. Asdescribed above, the host device 205 may interact with the data storagesystem 200 in accordance with a client/host model of informationdelivery.

The storage adapter 214 cooperates with the operating system 208executing on the node 202 to access information requested by the hostdevice 205 (e.g., access data on a storage device managed by a networkstorage controller). The information may be stored on any type ofattached array of writeable media such as magnetic disk drives, flashmemory, and/or any other similar media adapted to store information. Inthe example data storage system 200, the information can be stored indata blocks on the disks 224, 226, 228. The storage adapter 214 caninclude input/output (I/O) interface circuitry that couples to the disksover an I/O interconnect arrangement, such as a storage area network(SAN) protocol (e.g., Small Computer System Interface (SCSI), iSCSI,hyperSCSI, Fiber Channel Protocol (FCP)). The information is retrievedby the storage adapter 214 and, if necessary, processed by the one ormore processors 204 (or the storage adapter 214 itself) prior to beingforwarded over the system bus 242 to the network adapter 210 (and/or thecluster access adapter 212 if sending to another node in the cluster)where the information is formatted into a data packet and returned tothe host device 205 over the network 216 (and/or returned to anothernode attached to the cluster over the cluster fabric 215).

In one embodiment, storage of information on disk arrays 218, 220, 222can be implemented as one or more storage volumes 230, 232 that arecomprised of a cluster of disks 224, 226, 228 defining an overalllogical arrangement of disk space. The disks 224, 226, 228 that compriseone or more volumes are typically organized as one or more groups ofRAIDs. As an example, volume 230 comprises an aggregate of disk arrays218 and 220, which comprise the cluster of disks 224 and 226.

In one embodiment, to facilitate access to disks 224, 226, 228, theoperating system 208 may implement a file system (e.g., write anywherefile system) that logically organizes the information as a hierarchicalstructure of directories and files on the disks. In this embodiment,respective files may be implemented as a set of disk blocks configuredto store information, whereas directories may be implemented asspecially formatted files in which information about other files anddirectories are stored.

Whatever the underlying physical configuration within this data storagesystem 200, data can be stored as files within physical and/or virtualvolumes, which can be associated with respective volume identifiers,such as file system identifiers (FSIDs), which can be 32-bits in lengthin one example.

A physical volume corresponds to at least a portion of physical storagedevices whose address, addressable space, location, etc. doesn't change,such as at least some of one or more data storage devices 234 (e.g., aRedundant Array of Independent (or Inexpensive) Disks (RAID system)).Typically the location of the physical volume doesn't change in that the(range of) address(es) used to access it generally remains constant.

A virtual volume, in contrast, is stored over an aggregate of disparateportions of different physical storage devices. The virtual volume maybe a collection of different available portions of different physicalstorage device locations, such as some available space from each of thedisks 224, 226, and/or 228. It will be appreciated that since a virtualvolume is not “tied” to any one particular storage device, a virtualvolume can be said to include a layer of abstraction or virtualization,which allows it to be resized and/or flexible in some regards.

Further, a virtual volume can include one or more logical unit numbers(LUNs) 238, directories 236, Qtrees 235, and files 240. Among otherthings, these features, but more particularly LUNS, allow the disparatememory locations within which data is stored to be identified, forexample, and grouped as data storage unit. As such, the LUNs 238 may becharacterized as constituting a virtual disk or drive upon which datawithin the virtual volume is stored within the aggregate. For example,LUNs are often referred to as virtual drives, such that they emulate ahard drive from a general purpose computer, while they actually comprisedata blocks stored in various parts of a volume.

In one embodiment, one or more data storage devices 234 can have one ormore physical ports, wherein each physical port can be assigned a targetaddress (e.g., SCSI target address). To represent respective volumesstored on a data storage device, a target address on the data storagedevice can be used to identify one or more LUNs 238. Thus, for example,when the node 202 connects to a volume 230, 232 through the storageadapter 214, a connection between the node 202 and the one or more LUNs238 underlying the volume is created.

In one embodiment, respective target addresses can identify multipleLUNs, such that a target address can represent multiple volumes. The I/Ointerface, which can be implemented as circuitry and/or software in thestorage adapter 214 or as executable code residing in memory 206 andexecuted by the processors 204, for example, can connect to volume 230by using one or more addresses that identify the one or more LUNs 238.

It may be appreciated that storage tier verification checks may beimplemented for the data storage system 200. In an example, the node 202may utilize a multi-tier storage environment such as a remote objectstore and/or other storage tiers for serving client requests. It may beappreciated that storage tier verification checks may be implemented forand/or between any type of computing environment, and may betransferrable between physical devices (e.g., node 202, host device 205,a desktop computer, a tablet, a laptop, a wearable device, a mobiledevice, a storage device, a server, etc.) and/or a cloud computingenvironment (e.g., remote to the node 202 and/or the host device 205).

Various issues can arise when verifying consistency of a file system. Awafliron technique performs local checks to check sanity (e.g.,correctness) of any block without looking at any other block in afilesystem. Distributed checks are performed to verify the consistencyof the block by looking at different blocks in the filesystem. Aswafliron has to load multiple blocks as part of ironing a single block,client latencies goes up.

In one embodiment, lazy distributed checks are provided forverifying/ironing data. Ironing an entire file before providing accessto the file can cause clients to timeout because of the extensive amountof time taken to iron the entire file. Thus, the real time-to-dataavailability for files is when the whole file is completely ironed. Thisdepends on the size of the file and position of the file in the queuefor ironing. This amount of downtime is not acceptable for clients.Accordingly, as provided herein, enhanced avoidance techniques areprovided so that minimal checks/verifications in a client path can beperformed while leaving distributed checks to the background (e.g.,distributed checks to verify consistency of a block of data; distributedchecks of metafiles that may be interdependent upon one another, such asmetafiles used to manage the storage of data within multiple tiers ofstorage; etc.). That is, a focus is on how to decouple the distributedchecks from a frontend (e.g., a frontend that interfaces with clients).

The following are some of the distributed checks that iron does whichresults in client latencies going up. One example relates to claiming ablock. Whenever wafliron sees a block in an indirect it claims the blockby setting a bit in its status file. This will help in detecting doublylinked blocks. As part of doing this, wafliron has to load claimedstatus file. As part of ironing one indirect, wafliron might have toload around 255 claimed status file blocks. In case of vvol wafliron hasto load another 255*510 claimed status file blocks as wafliron has toverify container L1 corresponding to a vvbn. As part of claiming ablock, there is also a block accounting. This block accounting is neededto verify various on-disk space counters. Another example relates tocontainer pvbn checks. In case of vvols, a copy of the pvbn is cached inthe vvol indirect. So, wafliron has to go and verify if the pvbn presentin the vvol indirect is same as the one in the container file or not. Todo this, wafliron has to load the container L1

It may be desirable to stop these distributed checks. This is fine ifthere can only be hardware (HW) errors. HW errors are easy to detect, asany bitflips will cause checksum-error or WAFL lost-write checks willcatch other types of errors. But, software (SW) errors, which can occurbecause of logic bugs or scribbles, cannot be caught. So, enoughfilesystem avoidance features have been developed to prevent SW bugshitting the disk.

Because of deferring some distributed checks to background wafliron,there will be significant reduction in the client request latencies.Apart from reduction in client latencies, this feature also helps indefining quality of service (QOS) policies for wafliron. That is,wafliron currently tries to verify all the blocks before any block isreturned to clients. So, it's hard to control wafliron independently.This feature will make wafliron completely a background job withoutcoming in the way of client requests. This will help in having separateQOS policies for wafliron, i.e., letting wafliron run faster when thereis not much load on a filer/node or slowing down wafliron whenever thereis too much of load on the filer.

The feature brings a change in the perception of wafliron servingconsistent data. Even though inconsistent data can be served beforestarting wafliron, consistent and correct data will be served oncewafliron starts. This implies that data served while wafliron is runningwill remain unchanged. With this feature, as wafliron will be running inthe background, data served to clients can change after it is served toclients. A window is extended where inconsistent data can be served frombeginning of wafliron to end of wafliron.

Accordingly, as provided herein, distributed checks are deferred to abackground along with new avoidance mechanism an incremental checksum(IC) and an incremental consistency checker (ICC) being provided. ICwill help in protecting against SW scribbles and ICC will help inprotecting against SW logic bugs.

There could be hardware errors or logic bugs which can escape avoidancelayer and so a check is performed to make sure that there are no localinconsistencies. These local checks should be done before giving firstaccess to the clients. This is detailed version of metadata checks,which verifies all the indices for indirect blocks. Additional/detailedchecks are done on some metafile L0 blocks too. This is enabled only ondebug builds or in non-debug builds when wafliron is running. In debugbuilds, performance regression is a non-issue and in return there can bea catch more corruption scenarios. During wafliron, lazy distributedchecks (LDC) depends on this feature to detect all the localinconsistencies before the buffer is handed over to load path. So, LDCwill perform full local checks in this case.

In one example of lazy distributed check where wafliron interactionissues with other operations, wafliron was tightly integrated with therest of a file system, i.e., wafliron accounting is kept in sync withnew allocations and frees that happen in the file system. This requiredwafliron to do distributed checks before any modifications to the block.By moving the distributed checks to the background, allocation and freepath has to be taught whether a particular buffer has been checked byiron or not. Given that a file system free path has multiple stages toreally free a block, information about a block being ironed or not hasto be carried over to all the stages, which is what increases thecomplexity of the solution. Some other operations like moving thebuftree from one file to another file also has interaction withwafliron's distributed checks. As this is complex to resolve, no LDC isperformed during these operations. For inode/volume block accounting, asthere cannot be any new writes to a block before it is ironed, oldapproach of block accounting doesn't differentiate between old blocksand new blocks that got allocated while ironing. Not differentiatingwill result in reporting new writes as corruption. So, block accountingin iron has been modified to differentiate between old and new blocks.

In one example of making a filesystem resilient to corruptions, inlinedistributed checks are provided. As writing comprehensive ICC may not bepossible in some instances, there can be some distributed checks thatare done in the client access. But, code should be made resilient tohandle these corruptions and also fix them. These checks are calledinline distributed checks. These checks will not add any latency to theclient path as zero extra blocks needs to be loaded for doing thesechecks.

Also, inode/volume block accounting is provided. There are some countersat the volume level which wafliron verifies. As new writes can happenbefore blocks are accounted by wafliron, there can be overflow orunderflow of these counters. So, block accounting code has to be maderesilient to not panic in these scenarios.

Also, index based ironing is provided as an enhancement to LDC. With oldLDC design, ironing of a buffer and writes to it were mutuallyexclusive. This resulted in client latencies going up while a particularbuffer is being ironed. Also, this old design has caused somefunctionality interaction issues and was fragile. Primary reason formaking writes and ironing mutually exclusive is because of thegranularity at which iron information was stored. In the earlier design,iron information was stored at the block level and so till all indicesare ironed, no operations which want to know if block is ironed or nothave to be suspended. Ironing a block requires all indices to be ironed,which can take lot of time. So, if a higher level indirect is beingironed, no one under that parent can be dirtied till iron is completelydone. Accordingly, the granularity of iron information is changed fromblock level to an index. This helps in allowing client operations evenwhile a block is being ironed. In performance runs, there is a benefitof 100% throughput increase and 70% latency reduction with this feature.

LDC and index based ironing may be used to verify data and metadataassociated with tiering data between multiple tiers of storage. Forexample, LDC and index based ironing may be used to verify/ironmetafiles, buftree layouts, and/or other data used to manage the storageof data within a multi-tier storage environment.

One embodiment of storage tier verification checks is illustrated by anexemplary method 300 of FIG. 3. A storage system may provide clientswith access to client data stored within a backend such as a multi-tierstorage environment. The backend may be configured with one or moretiers of storage. For example, the backend may be configured with afirst storage tier (e.g., a performance tier, solid state drives, harddisk drives, etc.), a second storage tier such as a remote object store(e.g., a third party storage provider, a capacity tier, cloud storage,etc.), etc.

The storage system may store data within the first storage tier as aperformance tier for frequently or recently accessed data because thefirst storage tier may have lower latency and more guarantees than thesecond storage tier such as the remote object store. The storage systemmay migrate data from the first storage tier to the second storage tier(e.g., less frequently or less recently accessed data) or may store newdata to the remote object store. In an example, the first storage tiercomprises storage devices hosted by a storage environment of the storagesystem (e.g., clusters of nodes may store data with storage devicesowned and managed by such nodes) that manages client access to volumeswhose data is stored across the multi-tier storage environment. Thesecond storage tier comprises a remote object store hosted by a thirdparty storage provider and not the storage environment. The firststorage tier may have lower latency and improved consistency guaranteesthan the second storage tier because the storage environment hosts andmanages the first storage tier.

The storage system may create a composite aggregate composed of a set ofvolumes that are exposed to clients. Data of the set of volumes may bestored within the multi-tier storage environment such as within thefirst storage tier and as objects within the remote object store of thesecond storage tier. An object may be assigned a name based upon avolume identifier of a volume (e.g., a buftree UUID uniquely identifyingthe volume), of the composite aggregate, to which the object belongs.For example, a prefix of the name may be derived from the volumeidentifier. The name may also be derived from a sequence number uniquelyassigned to the object. For example, the prefix of the name may bederived from the sequence number. Monotonically increasing sequencenumbers may be assigned to objects that are created within the remoteobject store for a volume (e.g., sequence numbers may be unique for aparticular buftree UUID, but not across buftree UUIDs of other volumes).In an example, the name of the object may be derived from a hash for thevolume identifier and/or the sequence number.

The storage system may store objects within the remote object store. Anobject may comprise a header. The header may comprise a version of theobject, an indicator as to whether the object is encrypted, a creationtimestamp for the object, a volume identifier (e.g., a buftree universalidentifier such as a buftree UUID), an identifier of a name of theobject (e.g., a hash of the name and the buftree UUID, which can be readback after a put operation of the object into the remote object store toverify the hash), and/or other information. In one example, the headeris 32 bytes or any other size of information.

The object may comprise one or more object pages corresponding to datachunks, such as data chunks derived from data moved from the firststorage tier (e.g., a performance storage tier, such as a solid statestorage tier or a disk storage tier) of the storage system to the remoteobject store. In one example, the object may comprise space for 1024object pages, such as a first object page, a second object page, and/orother object pages. The first object page may comprise a first datachunk (e.g., 4 kilobytes of data or any other size of data) and a firstcontext associated with the first object page.

In one example, the object may be assembled within a staging areametafile stored within the first storage tier. An object slot mayrepresent the 1024 object pages into which data (e.g., data havingphysical volume block numbers (pvbns) of the first storage tier) isstored. Once the 1024 object pages are filled with data, the object isthen assembled and tiered (e.g., stored) into the remote object store.It may be appreciated that the object slot may comprise any number ofobject pages and is not limited to 1024. It may be appreciated that anobject slot may also be referred to as a block range within the stagingarea metafile.

The first context may comprise an indicator as to whether the object isencrypted. The first context may comprise an encryption key index usedto identify an encryption key. The first context may comprise apseudobad indicator to indicate whether data read from the local storagetier had an error such as a disk error and the data content in theobject is inconsistent. The first context may comprise an indicator asto whether a RAID or storage OS marked the pseudobad error. The firstcontext may comprise an unverified error indicator to indicate that whendata read from the local storage tier resulted in an unverified RAIDerror. The first context may comprise a wrecked indicator that is setwhen data is forcefully corrupted. The first context may comprise a fileblock number (e.g., a location of the file block number for the firstdata chunk within the first volume). The first context may comprise achecksum for the first data chunk and the first context. In an example,the first context may comprise 16 bytes of information or any other sizeof information.

The storage system may maintain metafiles used to track informationrelated to the creation of objects and the storage of objects to theremote object store of the multi-tiered storage environment. A volumeinformation metafile 402, a staging area information metafile 404, anobject reference metafile 406, an object information metafile 408, astaging area metafile 410, and/or an object map metafile 412 may bemaintained.

The volume information metafile 402 may comprise volume informationentries for a set of volumes of the aggregate (e.g., a first volumeinformation entry for a first volume, a second volume information entryfor a second volume, etc.). A volume information entry for a volume maycomprise a volume identifier of the volume. The volume information entrymay comprise a last assigned sequence number to the latest objectcreated for the volume (e.g., monotonically increasing sequence numbersmay be created and used to uniquely name objects of the volume). Thevolume information entry may comprise an object count of a number ofobjects of the volume stored within the remote object store. The volumeinformation entry may comprise other information related to volumesand/or to storing objects within the remote object store, such aswhether information is valid (e.g., a volume could be deleted but somevolume information metafile data could remain).

The staging area metafile 410 may comprise object slots for objects thatare to be assembled for tiering to the remote object store. For example,an object slot may comprise 1024 blocks (e.g., 1024 object pages) or anyother number of blocks (e.g., 1024 file block numbers or physical volumeblock numbers (pvbns) of data within a first storage tier of themulti-tiered storage environment that is different than the remoteobject store, such as where the staging area metafile 410 is storedwithin the first storage tier for the assembly of objects that are thenstored from the staging area metafile 410 within the first storage tierto the remote object store) into which data belonging to a particularvolume can be stored. Once the 1024 blocks are full, then the object isassembled and stored to the remote object store. In one example, onlyblocks that belong to the same volume will be stored into an object slotused to assemble an object. In this way, that object belongs to thatvolume. When an object slot for an object is put into the staging areametafile 410, an object identifier is assigned to the object. In thisway, the staging area metafile 410 is used to store data (e.g., 1024pvbns per object) that will be assembled into an assembled object forstorage into the remote object store. Object slots may have variousstates, such as empty, assembling where at least one block (e.g., objectpage) has been filled within an object slot, or full and ready to tierout to the remote object store. Because the aggregate may comprisemultiple volumes, multiple object slots can be in process for assembly.The staging area metafile 410 may comprise other information related tostoring objects within the remote object store.

The staging area information metafile 404 may comprise staging areainformation entries for object slots within the staging area metafile410. A staging area information entry comprises an object slot state(e.g., an empty state, a created state of being partially assembled withat some least blocks (e.g., object pages) within an object slot filled,or a ready to tier state where all blocks have been filled with data).The staging area information entry comprises an assigned objectidentifier that has been assigned for an object to be assembled fromdata within the object slot (e.g., a name or identifier of an object maybe derived from a sequence number for the object and/or a volumeidentifier of a volume to which data of the object to be assembledbelongs). The staging area information entry comprises the volumeidentifier of the volume to which data of the object to be assembledbelongs. The staging area information metafile 404 may comprise otherinformation related to assembling and/or storing objects to the remoteobject store.

The object information metafile 408 may comprise object informationentries indexed by object identifiers. An object information entry foran object identifier of an object comprises a volume identifier of avolume to which the object belongs. The object information entrycomprises a sequence number assigned to the object. The objectinformation entry comprises a state of the object identifier (e.g., afree state where the object identified has not been allocated/used buthas an object slot within the staging area metafile 410; a creatingstate for an object being assembled, a valid state of an object alreadystored into the remote object store, a waiting state, etc.). The objectinformation metafile 408 may comprise other information related tocreating and/or storing objects to the remote object store.

The object reference metafile 406 may specify numbers of references fromthe aggregate or a volume of the aggregate to object identifiers ofobjects. For example, object reference metafile 406 may specify how manyplaces in the aggregate are pointing to an object since an object canhave 1024 blocks of data and thus could have up to 1024 pointers withdifferent pvbns from the first storage tier where the block aretemporarily staged within the staging area metafile 410 stored withinthe first storage tier. In an example, the object reference metafile 406is a bitmap. In another example, the object reference metafile 406comprises a 32 bit number (or any other size) for each object identifierto indicate the number of references to corresponding objects. Theobject reference metafile 406 may comprise other information related tocreating and/or storing objects to the remote object store.

The object map metafile 412 may comprise bits set to indicate whetherobject identifiers of objects are allocated or not allocated. Forexample, the object map metafile 412 may comprise 1 bit per objectidentifier. The bit may be set to a first value to indicate that theobject identifier is allocated. The bit may be set to a second value toindicate that the object identifier is not allocated and is free. Thereis a one-to-one correspondence between the object reference metafile 406and the object map metafile 412.

Some metafiles may be verified during a mount operation, while othermetafiles may be verified after the mount operation. Distributed checksmay be performed upon information from multiple metafiles forverification due to reliance/interdependence between metafiles.

During the mount operation, the volume information metafile 402 and/orthe staging area information metafile 404 may be verified 506, asillustrated in FIG. 5. In one example, indirect blocks and/or otherbasic volume information (e.g. header magic) within the volumeinformation metafile 402 is verified (e.g., checked against informationwithin other metafiles such as the staging area information metafile404). After mount, object counts, last assigned sequence numbers, and/orother information in the volume information metafile 402 is verified. Inanother example, indirect blocks and/or other basic staging areainformation (e.g., header magic) within the staging area informationmetafile 404 is verified. After mount, object slot states, assignedobject identifiers, and/or volume identifiers may be verified. Anyinconsistencies or errors can be addressed, such as by modifying thevolume information metafile 402 and/or the staging area informationmetafile 404. Upon completion of the mount operation, client access todata of the aggregate may be provided.

At 302 of FIG. 3, a determination may be made that the mount operationof the aggregate has completed. At 304, a first metafile, a secondmetafile, and/or other metafiles such as the volume information metafile402, the staging area information metafile 404, the object referencemetafile 406, the object information metafile 408, the staging areametafile 410, and/or the object map metafile 412 may be maintained. At306, a distributed verification between the first metafile and thesecond metafile may be performed to identify an inconsistency based upona first set of storage information of the first metafile not beingconsistent with a second set of storage information of the secondmetafile. During the distributed verification, a garbage collectionprocess configured to perform garbage collection of old data storedwithin the remote object store (e.g., freeing/deallocating blocks nolonger used to store active data), a mirroring process configured tomirror data from a source to a destination, a tiering process configuredto tier data between the first storage tier of the multi-tier storageenvironment (e.g., where the metafiles are locally stored and whereobjects are assembled) and the remote object store (e.g., where objectsare remotely stored), and/or other processes that may otherwise modifymetafile data may be blocked or suspended. Client access to theaggregate may be facilitated during the distributed verifications (e.g.,clients may read data and/or write data to the multi-tier storageenvironment (e.g., clients may be allowed to only write to a localstorage tier) during the distributed verifications). At 308, areconciliation of the first set of storage information and the secondset of storage information may be performed to make the first metafileand the second metafile consistent. Client reads can be served andclient access to metafiles not yet completely verified (e.g., ironedout) can be facilitated by utilizing the lazy distributed checks ofmerely verifying (e.g., ironing) paths that are required to serve theclient reads.

In one example of performing a verification after completion of themount operation, a buftree verification 602 of files may be performed todetermine whether buftree layouts of the files are correct, asillustrated in FIG. 6. For example, the buftree verification 602 may beperformed for a buftree layout 600 corresponding to a hierarchicalstructure of blocks and/or indirect blocks that can be traversed toaccess a target data block.

In one example of performing a distributed verification, a verification706 is performed for the staging area information metafile 404 and/orthe staging area metafile 410, as illustrated in FIG. 7. For each objectslot of the staging area metafile 410 (e.g., an object slotcorresponding to a 1024 block range (e.g., 1024 object pages) to storepvbns of data to assemble into an object for storage into the remoteobject store), the staging area metafile 410 is evaluated to determine afirst status of blocks (e.g., object pages) sorted within the objectslot (e.g., a count of blocks that the staging area metafile 410 thinksare filling the 1024 block range). The staging area information metafile404 may be evaluated to determine a second status of blocks assigned tothe object slot (e.g., a count of blocks that the staging areainformation metafile 404 thinks are filling the 1024 block range or astatus indicating that either zero blocks have been assigned (e.g., anavailable status) or at least one block as being assigned (e.g., acreating/assembling status)). A reconciliation may be performed so thatthe first status and the second status are consistent in response to thefirst status not matching or corresponding to the second status (e.g.,the object slot state may be changed to a different state, data withinthe block range may be cleared, etc.).

In one example of performing a distributed verification, a verification806 is performed for the staging area information metafile 404 and/orthe object information metafile 408, as illustrated in FIG. 8. Forrespective object identifiers within the object information metafile 408(e.g., each object information entry corresponds to an object identifierof an object), a state of an object may be determined as being acreating state. The creating state may indicate that at least one blockhas filled some of a 1024 block range of an object slot for assemblingthe object. The staging area information metafile 404 (e.g., which mayhave been previously verified and made consistent by the verification706 of FIG. 7) may be queried using the object identifier to determine autilization state (e.g., an object slot state) of the object slot of theobject. Responsive to the utilization state indicating that the objectslot is available, the creating state within the object informationmetafile 408 is cleared to match the utilization state from the stagingarea information metafile 404. That is, the utilization state indicatingthat the object slot is available (does not comprise any data fillingthe 1024 block range) is inconsistent with the creating state indicatingthat at least one block has filled some of the 1024 block range. Becausethe staging area information metafile 404 may have been previouslyverified and made consistent by the verification 706 and comprises moreconsistent data, the utilization state within the staging areainformation metafile 404 is used to clear/update the state within theobject information metafile 408 in order to make the object informationmetafile consistent.

In one example of performing a distributed verification, a verification906 is performed for the volume information metafile 402 and/or theobject information metafile 408, as illustrated in FIG. 9. The volumeinformation metafile 402 may be queried to identify the last assignedsequence number for the volume and the number of objects of the volumestored into the remote object store and/or other information. The objectinformation metafile 408 may be queried to identify a sequence numberfor an object and/or other information. Responsive to the sequencenumber being greater than the last assigned sequence number and/or otherinformation being inconsistent, the last assigned sequence number withinthe volume information metafile 402 may be modified based upon thesequence number within the object information metafile 408 (e.g.,modifying sequence numbers to the larger of the two values to moveincrementally forward and not incrementally backward in sequencenumbers). In this way, the volume information metafile 402 may beverified and/or made consistent.

In one example of performing a distributed verification, a verification1006 is performed for the object reference metafile 406 and/or theobject map metafile 412, as illustrated in FIG. 10. A shadow copy of theobject reference metafile, specifying numbers of references (e.g.,pointers) from the aggregate or a volume to object identifiers ofobjects, may be created. A file system of the volume of the aggregatemay be walked through using the shadow copy to increment objectreference counts of objects references through the volume to create ashadow object reference file 1008. The shadow object reference file 1008is an up-to-date (e.g., correct) indicator of how many times objects arereferenced by the aggregate such as by the volume. The object referencemetafile 406 may be updated to match the shadow object reference file1008.

The object map metafile 412, comprising bits set to indicate whetherobject identifiers of objects are allocated, is updated based upon theshadow object reference file 1008. For example, a bit is set to indicatethat an object identifier is allocated based upon the shadow objectreference file 1008 indicating that the object identifier has an objectreference count greater than 0.

In one embodiment of performing a lazy distributed check, a request isreceived from a client to access a data block of a file associated witha tree structure representing data blocks of the file (e.g., ahierarchical structure of direct blocks, indirect blocks, etc.). A setof blocks that will be encountered for traversing the tree structure toreach the data block may be identified. Instead of verifying the entiretree structure, merely the set of blocks are verified. For example,verification is performed upon indexes of the set of blocks. In anotherexample, merely the data block is verified (e.g., an index is used todirectly identify the data block in the tree structure). Upon successfulverification of the set of blocks, access is provided to the data block.

In one embodiment, an avoidance mechanism, such as an incrementalchecksum and an incremental consistency checker, are provided to deferdistributed checks to a background processing state. The incrementalchecksum aids in protecting against software scribbles and theincremental consistency checker helps protect against software logicalbugs. An incremental checksum is provided to identify illegalmodifications to a buffer by regulating all legal modifications throughstandard interfaces and maintaining an up-to-date checksum of the wholebuffer incrementally each time the buffer is modified. An illegal (e.g.,random scribble) modification will be stopped by the standard interfaceand will not update the checksum appropriately. At the time of writing acorresponding block to disk, a checksum of the entire buffer is computedand compared against the maintained checksum. If there is not a match,then the buffer has been modified without updating the checksum.

An incremental consistency checker records incremental updates tobuftree indirects through an indirect update API. Whenever a childvirtual block number (vbn) is updated in an indirect, the incrementalconsistency checker tracks the old vbn as freed and the new vbn asallocated. An assigned vbn (wb_vol_bno) of an indirect is tracked. If afreed indirect's newly assigned vbn is not in a set of vbns going downto disk, then an accounting is made to ensure all of its children areaccounted as free. For example with a truncated indirect, there is noupdate to the indirect itself but the children are freed.

Each free is accounted as a decrement in a refcount (e.g., a count ofreferences to a block) and each allocation is accounted as an incrementto the refcount. When a bitmap block is going to disk, there is a checkthat the increment or decrement accounted for is the same an incrementor decrement in the bitmap buffer. To reduce performance overhead of thecomparisons, they can be done at time of a raid checksum computation.Using the indirect update, APIs can account the blocks at the inodelevel. These per inode counters are matched with a delta of the actualcounts in inodes going to disk.

In one example, hardware errors or logical bugs can escape avoidancelayer. Accordingly, local checks are done so that there are no localinconsistencies. These local checks are done before giving access toclients. This is a version of metadata checks, which verifies allindices for indirect blocks. Some additional checks are done on metafileL0 blocks to enable for debug builds and non-debug builds.

In one example, inline distributed checks are performed for clientaccess. Such checks do not add latency to a client path as zero extrablocks are loaded for doing these checks. In another example,inode/volume block accounting is performed. Some counters at a volumelevel are verified. As new writes can happen before blocks are accountedfor, there can be overflow or underflow of these counters. So, blockaccounting code is made resilient to not panic in such scenarios. Inanother example, index based verification is provided where verificationis provided at an index level instead of a block level, which helpsallow client operations to run even while a block is being verified.

Still another embodiment involves a computer-readable medium comprisingprocessor-executable instructions configured to implement one or more ofthe techniques presented herein. An example embodiment of acomputer-readable medium or a computer-readable device that is devisedin these ways is illustrated in FIG. 11, wherein the implementation 1100comprises a computer-readable medium 1108, such as a compactdisc-recordable (CD-R), a digital versatile disc-recordable (DVD-R),flash drive, a platter of a hard disk drive, etc., on which is encodedcomputer-readable data 1106. This computer-readable data 1106, such asbinary data comprising at least one of a zero or a one, in turncomprises a processor-executable computer instructions 1104 configuredto operate according to one or more of the principles set forth herein.In some embodiments, the processor-executable computer instructions 1104are configured to perform a method 1102, such as at least some of theexemplary method 300 of FIG. 3, for example. In some embodiments, theprocessor-executable computer instructions 1104 are configured toimplement a system, such as at least some of the exemplary system 400 ofFIG. 4, at least some of the exemplary system 500 of FIG. 5, at leastsome of the exemplary system 600 of FIG. 6, at least some of theexemplary system 700 of FIG. 7, at least some of the exemplary system800 of FIG. 8, at least some of the exemplary system 900 of FIG. 9,and/or at least some of the exemplary system 1000 of FIG. 10, forexample. Many such computer-readable media are contemplated to operatein accordance with the techniques presented herein.

It will be appreciated that processes, architectures and/or proceduresdescribed herein can be implemented in hardware, firmware and/orsoftware. It will also be appreciated that the provisions set forthherein may apply to any type of special-purpose computer (e.g., filehost, storage server and/or storage serving appliance) and/orgeneral-purpose computer, including a standalone computer or portionthereof, embodied as or including a storage system. Moreover, theteachings herein can be configured to a variety of storage systemarchitectures including, but not limited to, a network-attached storageenvironment and/or a storage area network and disk assembly directlyattached to a client or host computer. Storage system should thereforebe taken broadly to include such arrangements in addition to anysubsystems configured to perform a storage function and associated withother equipment or systems.

In some embodiments, methods described and/or illustrated in thisdisclosure may be realized in whole or in part on computer-readablemedia. Computer readable media can include processor-executableinstructions configured to implement one or more of the methodspresented herein, and may include any mechanism for storing this datathat can be thereafter read by a computer system. Examples of computerreadable media include (hard) drives (e.g., accessible via networkattached storage (NAS)), Storage Area Networks (SAN), volatile andnon-volatile memory, such as read-only memory (ROM), random-accessmemory (RAM), electrically erasable programmable read-only memory(EEPROM) and/or flash memory, compact disk read only memory (CD-ROM)s,CD-Rs, compact disk re-writeable (CD-RW)s, DVDs, cassettes, magnetictape, magnetic disk storage, optical or non-optical data storage devicesand/or any other medium which can be used to store data.

Although the subject matter has been described in language specific tostructural features or methodological acts, it is to be understood thatthe subject matter defined in the appended claims is not necessarilylimited to the specific features or acts described above. Rather, thespecific features and acts described above are disclosed as exampleforms of implementing at least some of the claims.

Various operations of embodiments are provided herein. The order inwhich some or all of the operations are described should not beconstrued to imply that these operations are necessarily orderdependent. Alternative ordering will be appreciated given the benefit ofthis description. Further, it will be understood that not all operationsare necessarily present in each embodiment provided herein. Also, itwill be understood that not all operations are necessary in someembodiments.

Furthermore, the claimed subject matter is implemented as a method,apparatus, or article of manufacture using standard application orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer application accessible from anycomputer-readable device, carrier, or media. Of course, manymodifications may be made to this configuration without departing fromthe scope or spirit of the claimed subject matter.

As used in this application, the terms “component”, “module,” “system”,“interface”, and the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentincludes a process running on a processor, a processor, an object, anexecutable, a thread of execution, an application, or a computer. By wayof illustration, both an application running on a controller and thecontroller can be a component. One or more components residing within aprocess or thread of execution and a component may be localized on onecomputer or distributed between two or more computers.

Moreover, “exemplary” is used herein to mean serving as an example,instance, illustration, etc., and not necessarily as advantageous. Asused in this application, “or” is intended to mean an inclusive “or”rather than an exclusive “or”. In addition, “a” and “an” as used in thisapplication are generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform. Also, at least one of A and B and/or the like generally means A orB and/or both A and B. Furthermore, to the extent that “includes”,“having”, “has”, “with”, or variants thereof are used, such terms areintended to be inclusive in a manner similar to the term “comprising”.

Many modifications may be made to the instant disclosure withoutdeparting from the scope or spirit of the claimed subject matter. Unlessspecified otherwise, “first,” “second,” or the like are not intended toimply a temporal aspect, a spatial aspect, an ordering, etc. Rather,such terms are merely used as identifiers, names, etc. for features,elements, items, etc. For example, a first set of information and asecond set of information generally correspond to set of information Aand set of information B or two different or two identical sets ofinformation or the same set of information.

Also, although the disclosure has been shown and described with respectto one or more implementations, equivalent alterations and modificationswill occur to others skilled in the art based upon a reading andunderstanding of this specification and the annexed drawings. Thedisclosure includes all such modifications and alterations and islimited only by the scope of the following claims. In particular regardto the various functions performed by the above described components(e.g., elements, resources, etc.), the terms used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., that is functionally equivalent), even though notstructurally equivalent to the disclosed structure. In addition, while aparticular feature of the disclosure may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.

What is claimed is:
 1. A method, comprising: determining that a mountoperation of an aggregate comprising a set of volumes stored within amulti-tier storage environment has completed, wherein data of a volumeis stored within one or more objects within a remote object store of themulti-tier storage environment, wherein the mount operation comprisesverifying a volume information metafile comprising volume informationentries for the set of volumes, wherein a volume information entryspecifies a volume identifier of the volume, a last assigned sequencenumber for an object of the volume stored to the remote object store,and a number of objects of the volume stored within the remote objectstore; performing a distributed verification, between a first metafileand a second metafile used to track information related to the storageof objects within the remote object store, to identify an inconsistencybased upon a first set of storage information of the first metafile notbeing consistent with a second set of storage information of the secondmetafile; and reconciling the first set of storage information and thesecond set of storage information to make the first metafile and thesecond metafile consistent.
 2. The method of claim 1, wherein theperforming a distributed verification comprises: facilitating clientaccess to the volume during the distributed verification.
 3. The methodof claim 1, wherein the performing a distributed verification comprises:blocking a garbage collection process, configured to perform garagecollection of old data stored within the remote object store, during thedistributed verification.
 4. The method of claim 1, wherein theperforming a distributed verification comprises: blocking a mirroringprocess, configured to mirror data from a source to a destination,during the distributed verification.
 5. The method of claim 1, whereinthe performing a distributed verification comprises: blocking a tieringprocess, configured to tier data between a storage tier of themulti-tier storage environment and the remote object store, during thedistributed verification.
 6. The method of claim 1, wherein theverifying the volume information metafile comprises: modifying orclearing information within the volume information metafile to addressan inconsistency identified within the volume information metafile. 7.The method of claim 1, comprising: verifying a staging area informationmetafile during the mount operation, wherein the staging areainformation metafile comprises staging area information entries forobject slots within a staging area metafile, wherein a staging areainformation entry specifies an object slot state of an object slot usedto store data for assembly into an assembled object, an assigned objectidentifier for the assembled object, and the volume identifier of thevolume to which the assembled object belongs.
 8. The method of claim 1,comprising: performing a buftree verification of files to determinewhether buftree layouts of the files are correct.
 9. The method of claim8, comprising: allowing a client access operation to be performed duringthe buftree verification.
 10. A non-transitory machine readable mediumcomprising instructions for performing a method, which when executed bya machine, causes the machine to: determine that a mount operation of anaggregate comprising a set of volumes stored within a multi-tier storageenvironment has completed, wherein data of a volume is stored within oneor more objects within a remote object store of the multi-tier storageenvironment, wherein the mount operation comprises verifying a stagingarea information metafile comprising staging area information entriesfor object slots within a staging area metafile, wherein a staging areainformation entry specifies an object slot state of an object slot usedto store data for assembly into an assembled object, an assigned objectidentifier for the assembled object, and a volume identifier of thevolume to which the assembled object belongs; perform a distributedverification, between a first metafile and a second metafile used totrack information related to the storage of objects within the remoteobject store, to identify an inconsistency based upon a first set ofstorage information of the first metafile not being consistent with asecond set of storage information of the second metafile; and reconcilethe first set of storage information and the second set of storageinformation to make the first metafile and the second metafileconsistent.
 11. The non-transitory machine readable medium of claim 10,wherein the instructions cause the machine to: facilitate client accessto the volume during the distributed verification.
 12. Thenon-transitory machine readable medium of claim 10, wherein theinstructions cause the machine to: block a garbage collection process,configured to perform garage collection of old data stored within theremote object store, during the distributed verification.
 13. Thenon-transitory machine readable medium of claim 10, wherein theinstructions cause the machine to: block a mirroring process, configuredto mirror data from a source to a destination, during the distributedverification.
 14. The non-transitory machine readable medium of claim10, wherein the instructions cause the machine to: block a tieringprocess, configured to tier data between a storage tier of themulti-tier storage environment and the remote object store, during thedistributed verification.
 15. The non-transitory machine readable mediumof claim 10, wherein the instructions cause the machine to: verify avolume information metafile during the mount operation, wherein thevolume information metafile comprises volume information entries for theset of volumes, wherein a volume information entry specifies the volumeidentifier of the volume, a last assigned sequence number for an objectof the volume stored to the remote object store, and a number of objectsof the volume stored within the remote object store.
 16. Thenon-transitory machine readable medium of claim 10, wherein theinstructions cause the machine to: modify or clear information withinthe staging area information metafile to address an inconsistencyidentified within the staging area information metafile by theverification.
 17. The non-transitory machine readable medium of claim10, wherein the instructions cause the machine to: perform a buftreeverification of files to determine whether buftree layouts of the filesare correct.
 18. The non-transitory machine readable medium of claim 17,wherein the instructions cause the machine to: allow a client accessoperation to be performed during the buftree verification.
 19. Acomputing device comprising: a hardware memory comprising machineexecutable code; and a hardware processor coupled to the hardwarememory, the hardware processor configured to execute the machineexecutable code to cause the computing device to: perform a mountoperation of an aggregate comprising a set of volumes of data storedwithin one or more objects within a remote object store, wherein averification is performed during the mount operation for a staging areainformation metafile comprising staging area information entries forobject slots within a staging area metafile, wherein a staging areainformation entry specifies an object slot state of an object slot usedto store data for assembly into an assembled object, an assigned objectidentifier for the assembled object, and a volume identifier of thevolume to which the assembled object belongs; perform a distributedverification, between a first metafile and a second metafile used totrack information related to the storage of objects within the remoteobject store, to identify an inconsistency based upon a first set ofstorage information of the first metafile not being consistent with asecond set of storage information of the second metafile; and reconcilethe first set of storage information and the second set of storageinformation to make the first metafile and the second metafileconsistent.
 20. The computing device of claim 19, wherein the machineexecutable code causes the computing device to: facilitate client accessto the volume during the distributed verification.
 21. A method,comprising: determining that a mount operation of an aggregatecomprising a set of volumes stored within a multi-tier storageenvironment has completed, wherein data of a volume is stored within oneor more objects within a remote object store of the multi-tier storageenvironment, wherein the mount operation comprises verifying a stagingarea information metafile comprising staging area information entriesfor object slots within a staging area metafile, wherein a staging areainformation entry specifies an object slot state of an object slot usedto store data for assembly into an assembled object, an assigned objectidentifier for the assembled object, and a volume identifier of thevolume to which the assembled object belongs; performing a distributedverification, between a first metafile and a second metafile used totrack information related to the storage of objects within the remoteobject store, to identify an inconsistency based upon a first set ofstorage information of the first metafile not being consistent with asecond set of storage information of the second metafile; andreconciling the first set of storage information and the second set ofstorage information to make the first metafile and the second metafileconsistent.
 22. The method of claim 21, comprising: modifying orclearing information within the volume information metafile to addressan inconsistency identified within the volume information metafile. 23.The method of claim 21, comprising: blocking a garbage collectionprocess, configured to perform garage collection of old data storedwithin the remote object store, during the distributed verification. 24.A method, comprising: performing a mount operation of an aggregatecomprising a set of volumes of data stored within one or more objectswithin a remote object store, wherein a verification is performed duringthe mount operation for a staging area information metafile comprisingstaging area information entries for object slots within a staging areametafile, wherein a staging area information entry specifies an objectslot state of an object slot used to store data for assembly into anassembled object, an assigned object identifier for the assembledobject, and a volume identifier of the volume to which the assembledobject belongs; performing a distributed verification, between a firstmetafile and a second metafile used to track information related to thestorage of objects within the remote object store, to identify aninconsistency based upon a first set of storage information of the firstmetafile not being consistent with a second set of storage informationof the second metafile; and reconciling the first set of storageinformation and the second set of storage information to make the firstmetafile and the second metafile consistent.
 25. The method of claim 24,comprising: modifying or clearing information within the volumeinformation metafile to address an inconsistency identified within thevolume information metafile.
 26. The method of claim 24, comprising:blocking a garbage collection process, configured to perform garagecollection of old data stored within the remote object store, during thedistributed verification.
 27. A non-transitory machine readable mediumcomprising instructions for performing a method, which when executed bya machine, causes the machine to: determine that a mount operation of anaggregate comprising a set of volumes stored within a multi-tier storageenvironment has completed, wherein data of a volume is stored within oneor more objects within a remote object store of the multi-tier storageenvironment, wherein the mount operation comprises verifying a volumeinformation metafile comprising volume information entries for the setof volumes, wherein a volume information entry specifies a volumeidentifier of the volume, a last assigned sequence number for an objectof the volume stored to the remote object store, and a number of objectsof the volume stored within the remote object store; perform adistributed verification, between a first metafile and a second metafileused to track information related to the storage of objects within theremote object store, to identify an inconsistency based upon a first setof storage information of the first metafile not being consistent with asecond set of storage information of the second metafile; and reconcilethe first set of storage information and the second set of storageinformation to make the first metafile and the second metafileconsistent.
 28. The non-transitory machine readable medium of claim 27,wherein the instructions cause the machine to: modify or clearinformation within the volume information metafile to address aninconsistency identified within the volume information metafile.
 29. Thenon-transitory machine readable medium of claim 27, wherein theinstructions cause the machine to: block a garbage collection process,configured to perform garage collection of old data stored within theremote object store, during the distributed verification.
 30. Anon-transitory machine readable medium comprising instructions forperforming a method, which when executed by a machine, causes themachine to: perform a mount operation of an aggregate comprising a setof volumes of data stored within one or more objects within a remoteobject store, wherein a verification is performed during the mountoperation for a staging area information metafile comprising stagingarea information entries for object slots within a staging areametafile, wherein a staging area information entry specifies an objectslot state of an object slot used to store data for assembly into anassembled object, an assigned object identifier for the assembledobject, and a volume identifier of the volume to which the assembledobject belongs; perform a distributed verification, between a firstmetafile and a second metafile used to track information related to thestorage of objects within the remote object store, to identify aninconsistency based upon a first set of storage information of the firstmetafile not being consistent with a second set of storage informationof the second metafile; and reconcile the first set of storageinformation and the second set of storage information to make the firstmetafile and the second metafile consistent.
 31. The non-transitorymachine readable medium of claim 30, wherein the instructions cause themachine to: modify or clear information within the volume informationmetafile to address an inconsistency identified within the volumeinformation metafile.
 32. The non-transitory machine readable medium ofclaim 30, wherein the instructions cause the machine to: block a garbagecollection process, configured to perform garage collection of old datastored within the remote object store, during the distributedverification.
 33. A computing device comprising: a hardware memorycomprising machine executable code; and a hardware processor coupled tothe hardware memory, the hardware processor configured to execute themachine executable code to cause the computing device to: determine thata mount operation of an aggregate comprising a set of volumes storedwithin a multi-tier storage environment has completed, wherein data of avolume is stored within one or more objects within a remote object storeof the multi-tier storage environment, wherein the mount operationcomprises verifying a staging area information metafile comprisingstaging area information entries for object slots within a staging areametafile, wherein a staging area information entry specifies an objectslot state of an object slot used to store data for assembly into anassembled object, an assigned object identifier for the assembledobject, and a volume identifier of the volume to which the assembledobject belongs; perform a distributed verification, between a firstmetafile and a second metafile used to track information related to thestorage of objects within the remote object store, to identify aninconsistency based upon a first set of storage information of the firstmetafile not being consistent with a second set of storage informationof the second metafile; and reconcile the first set of storageinformation and the second set of storage information to make the firstmetafile and the second metafile consistent.
 34. The computing device ofclaim 33, wherein the machine executable code causes the computingdevice to: modify or clear information within the volume informationmetafile to address an inconsistency identified within the volumeinformation metafile.
 35. The computing device of claim 33, wherein themachine executable code causes the computing device to: block a garbagecollection process, configured to perform garage collection of old datastored within the remote object store, during the distributedverification.
 36. A computing device comprising: a hardware memorycomprising machine executable code; and a hardware processor coupled tothe hardware memory, the hardware processor configured to execute themachine executable code to cause the computing device to: determine thata mount operation of an aggregate comprising a set of volumes storedwithin a multi-tier storage environment has completed, wherein data of avolume is stored within one or more objects within a remote object storeof the multi-tier storage environment, wherein the mount operationcomprises verifying a volume information metafile comprising volumeinformation entries for the set of volumes, wherein a volume informationentry specifies a volume identifier of the volume, a last assignedsequence number for an object of the volume stored to the remote objectstore, and a number of objects of the volume stored within the remoteobject store; perform a distributed verification, between a firstmetafile and a second metafile used to track information related to thestorage of objects within the remote object store, to identify aninconsistency based upon a first set of storage information of the firstmetafile not being consistent with a second set of storage informationof the second metafile; and reconcile the first set of storageinformation and the second set of storage information to make the firstmetafile and the second metafile consistent.
 37. The computing device ofclaim 36, wherein the machine executable code causes the computingdevice to: modify or clear information within the volume informationmetafile to address an inconsistency identified within the volumeinformation metafile.
 38. The computing device of claim 36, wherein themachine executable code causes the computing device to: block a garbagecollection process, configured to perform garage collection of old datastored within the remote object store, during the distributedverification.